Non-persistent heterogeneous neighbors

ABSTRACT

A heterogeneous network comprising macro network devices and micro network devices operates to maintain a dynamic data set of neighbor relations for a potential transfer of a User Equipment (UE) device from one network zone to another network zone. In response to detecting a failure of a macro network device to establish a network connection with a network device, a dynamic management of the data set initiates. A capacity number of network connections is determined for the macro network device (e.g., macro eNB sector carrier) based on the data set of neighbor relations. A threshold number is determined from the network neighbor device data, representing the set of micro network devices with which the macro network device is operable to establish the network. A defined number of micro network devices is maintained that is less than the threshold number of the network neighbor device data.

TECHNICAL FIELD

The subject disclosure relates to wireless communications and, inparticular, to heterogeneous network neighbors of wireless communicationnetworks.

BACKGROUND

Conventional macro network platforms that provide service to mobiledevices (e.g., user equipment (UE)) contend with mobility of the UE whenproviding communication services. Networks (e.g., long term evolution(LTE) technologies) utilize an automatic neighbor relations (ANR)feature to establish neighbor relations between nodes of the network(e.g., eNodeBs) based on measurement reports from UEs in the operatornetwork. Traditional ANR mechanisms are designed for single-layernetworks where cells are of similar size (e.g., macro network cells) andimportance for real-time mobility. Multi-layer heterogeneous networks,including macro cell networks, pico cell networks, Femto cell networks,Metro cell networks, etc., do not fit this model. Large cells may bepresented with additional, infrequently-used, small cell neighbors tomanage. If those small cell neighbor relations are persistent in nature,the large cell neighbor lists are truncated or can become too large tobroadcast in a timely fashion. This can prevent mobile stations fromidentifying sites that are potential handover candidates, and adverselyaffect mobile handover performance.

BRIEF DESCRIPTION OF THE DRAWINGS

Various non-limiting embodiments are further described with reference tothe accompanying drawings in which:

FIG. 1 illustrates an example, non-limiting wireless communicationsenvironment that can be utilized with the disclosed aspects;

FIG. 2 illustrates an example, non-limiting system for establishingneighbor relations with network devices for potential handover of UEdevices, according to an aspect;

FIG. 3 illustrates another example, non-limiting system for establishingneighbor relations with network devices for potential handover of UEdevices, according to an aspect;

FIG. 4 illustrates another example, non-limiting system for establishingneighbor relations with network devices for potential handover of UEdevices, according to an aspect;

FIG. 5 illustrates an example, non-limiting system for networkcommunications between communications network devices for potentialhandover of applications of a UE device, according to an aspect;

FIG. 6 illustrates an example, non-limiting method for managing neighborrelations among network devices, according to an aspect;

FIG. 7 illustrates another example, non-limiting method, for managingneighbor relations among network devices according to an aspect;

FIG. 8 illustrates another example, non-limiting method for managingneighbor relations among network devices, according to an aspect;

FIG. 9 is a schematic example wireless environment that can operate inaccordance with aspects described herein;

FIG. 10 illustrates a block diagram of access equipment and/or softwarerelated to access of a network, in accordance with an embodiment; and

FIG. 11 illustrates a block diagram of a computing system, in accordancewith an embodiment.

DETAILED DESCRIPTION

Aspects of the subject disclosure will now be described more fullyhereinafter with reference to the accompanying drawings that illustratedifferent example embodiments. In the following description, forpurposes of explanation, numerous specific details are set forth inorder to provide a thorough understanding of the various embodiments.However, the subject disclosure can embody many different forms andshould not be construed as limited to the example embodiments set forthherein.

The management of small cell relationships or neighbor relations amongmulti-heterogeneous networks can ensure less delay in identifying sitesor network devices having network coverage areas that are potentialhandover candidates. Network data (e.g., a network list, data store,network table, network candidate data or the like) can be utilized tostore network neighbor relations or communication connections forhandover potential among UEs. The network data can be dynamicallyupdated, resorted and managed based on various network dynamics witheach macro network cell device, the macro network neighbors and microcell neighbors (e.g., Femto cell network devices, pico cell networkdevices, metro cell network devices or other network devicesfacilitating a network coverage area for mobile communication). Forexample, the network data can be a list, or data store having potentialhandover candidates, in which the data can be updated as network devicesare added and deleted as potential handover candidates for the hand-offfrom one network to another network neighboring or having neighborrelations with the first network device. As a macro cell, for example,approaches or reaches a maximum amount of neighbor relations (neighborconnections), some neighbor relations can get dropped from the permanentlist or truncated to accommodate additional neighbors as potentialhand-over candidates. When these additional neighbors are not frequentlyused or have a low rate of attach attempts, dropping the neighborrelations of other cells can be an inefficient use of resources andcause delay among other UE's for potential hand-off.

In an aspect disclosed, an aggressive addition of neighbors is createdby UE discovery of candidates, cell network listening schemes, or otherautomated processes, while avoiding the danger of creating permanentneighbor lists that are too long to be broadcast in an efficient manneror too long for a managing server or UE to efficiently scan. This methodis particularly applicable to small-cells, Femto cells, closedsubscriber group (CSG) cells, or other controlled access cells, thathave small or restricted access coverage areas relative to a macronetwork device, and/or areas where there is pedestrian or low mobility,such that a very minor delay in hand-in to the cell caused by extrasignaling to set up the neighbor relation would not adversely affectcustomer-perceived performance.

In one embodiment, various methods allow for infrequently-used,ephemeral, or restricted access cells that have had neighbor relationscreated via an automated process such as ANR to be deleted after arelatively short delay of fixed, calculated, or operator settableduration with minimal impact on performance and signaling load. Thisfunctionality can be deliberately applied to the non-macro layers inorder to reduce impact and work with legacy macro systems. LTE and Femtospecific mechanisms are described, for example, but the intendedapplication is not limited to LTE or Femto. The embodiments herein canbe applied, for example, to many other network layers and technologiesthan LTE and Femto examples, such as with any macro cell network devicesand micro cell devices that comprise smaller coverage zones or coverageareas than the macro cell network devices. Macro LTE eNB (evolved nodeBs or macro cell devices that can comprise macro level network nodes) ormacro network cell devices can add and remove other LTE handoverneighbors according to the 3GPP ANR. In addition, the macro eNB (macronetwork cell device) does not differentiate heterogeneous networklayers, such as macro network devices and micro cell devices operatingas neighbors in the same network environment for these neighboradditions and deletions. These operations can be addressed via specificANR controls in the lower layer networks, specifically in Femto cellnetwork devices or other micro cell network devices or micro cellnetwork managing devices. Pertinent functionality is implemented forpotential hand-off or handover from one network cell device to anotherin three stages: 1) construct available neighbor history for macronetwork, 2) operate neighbor (neighbor candidates, neighbor connections)addition, and 3) neighbor prioritization and cleanup.

FIG. 1 illustrates an example, non-limiting wireless communicationsenvironment 100 in accordance with various embodiments described. Thewireless communications environment 100 can include a heterogeneousnetwork environment that has a multitude of wireless communicationsnetworks, each having a respective coverage area. The coverage area ofsome of the wireless communications networks can overlap such that oneor more network devices can provide coverage areas or zones to UEs ormobile devices whose coverage areas from different networks of networkdevices overlap. For example, a relatively large number of Femto accesspoint (FAP) can have overlapping/neighboring coverage with each macroeNB sector carrier and operate as potential handover candidates from onenetwork to another. The network devices of the heterogeneous networkenvironment can operate with one another as a self-organizing network(SON), in which at least some of the network devices can be configuredto provide self-configuration and self-optimizing capabilities thatprovide the ability to automate certain operations, management functionsand system management functions. The SON incorporatesself-configuration, self-optimization, monitoring, and operationmanagement to allow the network devices to be communicatively coupledinto the network and operate with little to no human intervention.

The wireless communications environment 100 includes one or more macro(cell) network devices 102, 104 that broadcast macro network zonecoverage areas and one or more micro network devices 106, 108 (e.g.,Pico network access point, Metro network access point, Femto networkaccess point, or other similar micro network access points) deployedwithin the wireless communications environment 100 and servicing one ormore UE devices 110, 112, 114, 116, 118 in corresponding networkcoverage zones. Each wireless communications network (e.g., macro accesspoints 102, 104 and micro access points 106, 108) comprises one or morenetwork devices (e.g., a set of network devices), such as base stationsthat operate in conjunction with one another in order to process networktraffic (e.g., handoff operations and coverage) for the one or more UEdevices 110, 112, 114, 116, or 118. The network devices (e.g., 102, 104,106, 108) can be neighbors within one another that overlap or havecoverage boundaries alongside or proximate to one another. For example,a number of FAPs or other micro network devices 106, 108 can overlap orhave neighboring coverage with each macro network device 102, 104respectively. The macro network devices 102, 104 can comprise a set ofnetwork devices that are cellular enabled network devices, which couldprovide different network speeds (e.g., 2G, 3G, 4G, etc.). In anotherexample, the micro access point devices 106, 108 can include a set ofnetwork devices that extend network coverage or expand the networkenvironment at the cell edge, especially where access would otherwise belimited or unavailable, and can include any standard such as for WCDMA,GSM, CDMA2000, TD-SCDMA, WiMAX, for LTE or other solutions.

The communications environment 100 can include one or more managementservers 130, 132 that are communicatively coupled to the network devicessuch as the macro network devices 102, 104 and the micro network devices106, 108 as a control-node for one or more networks. The managementservers 130, 132 can operatively control UE device tracking and pagingprocedures including retransmissions and handover (hand-off) operationsto ensure seamless mobility through various network zones within thenetwork environment 100. The management servers 130, 132 can control,for example, the bearer activation/deactivation process and choosing aserving gateway for the UE devices 110, 112, 114, 116, or 118 at theinitial attach and at the time of an intra-network handover (e.g., amongthe different networks, 4G to 3G, 3G to 3G or the like). Further, thenetwork devices (e.g., macro network devices 130, 132 or micro networkdevices 106, 108) can include the management server 130, 132respectively, and thus, these and other management operations can becontrolled by each network device itself with the management serversinternal or independently external to the network devices. Themanagement servers 130, 132 can authenticate UEs by interacting with theother devices communicatively coupled thereto and/or sets of dataservers such as a home subscriber server and the like. The managementservers 130, 132 can operate in conjunction with one or more backendpacket core components 134 having a processor and memory that canoperate to generate and allocate temporary identities to UEs andterminates Non-Access Stratum (NAS) signaling or other signalingprotocol layers. The NAS can be used to manage the establishment ofcommunication sessions (e.g., between UEs) and for maintainingcontinuous communications with the user equipment as the UE moves, suchas for hand-over operations from network device to network device. Themanagement servers 130, 132 can also manage signaling to the AccessStratum for carrying information over the wireless portion of thenetwork and security key management operations (e.g., authentication,verification, authorization operations) with UE application data and UEdevice functions. In particular, one or more of the managing servers130, 132 can operate to maintain and establish network relations via oneor more base stations or network devices via an X2 interface or as amobility management entity (MME) via an S1 interface, for example.

The communication environment 100 can operate to implement techniquesfor a heterogeneous network environment in a SON network that provideautomatic configuration of neighbor cell relations, such as ANR, forexample. The managing servers 130, 132 can operate as network devicesthat can facilitate ANR operations to configure discovered neighborrelations such that handovers can be performed in combination withneighbor relation establishment without dropping a UE connection to thenetworks of the network environment 100. In one example, the networkenvironment can comprises a LTE environment that can comprise one ormore evolved radio access networks (E-UTRAN) with corresponding networkdevices or macro network devices with micro network devices overlapping,and an evolved packet core, such as the backend packet core 134. Eachcell can be served by an eNodeB, eNB (base station) or other macronetwork device, in which handover can pass between the macro networkdevices 102, 104 and/or the smaller (micro) network devices 106, 108,for example.

As illustrated, each of the one or more micro access points 106, 108 canhave a corresponding service area 120, 122. In addition, each of the oneor more macro network devices 102, 104 can have a corresponding serviceor broadcast area 124, 126. However, the wireless communicationsenvironment 100 is not limited to this implementation and various otherarchitectures can also be employed. For example, the self-organizingnetwork devices of the communication environment 100 can deploy anynumber of Wi-Fi access points and respective service areas within thewireless communications environment 100, further comprise othermechanisms than LTE Femto-specific mechanisms or devices other than LTEor Femto, and comprise other network layers and technologies.

A UE device can contain some or all of the functionality of a system,subscriber unit, subscriber station, mobile station, mobile, wirelessterminal, device, mobile device, remote station, remote terminal, accessterminal, user terminal, terminal, wireless communication device,wireless communication apparatus, user agent, user device, or UE devicefor example. A mobile device or UE can be a cellular telephone, acordless telephone, a Session Initiation Protocol (SIP) phone, a smartphone, a feature phone, a wireless local loop (WLL) station, a personaldigital assistant (PDA), a laptop, a handheld communication device, ahandheld computing device, a netbook, a tablet, a satellite radio, adata card, a wireless modem card and/or another processing device forcommunicating over a wireless system. Each UE device 110, 112, 114, 116,118 can be served by the macro cell devices 102, 104, or micro celldevices 106, 108, in which handovers can be controlled by a networkdata, data store, a data set, a data list, neighbor relation table(NRT), or the like that is managed or maintained by the managing servers130, 132, a macro network device, a micro network device or the othernetwork device, for example. The UE devices 110, 112, 114, 116, 118 canrespectively broadcast an identifying signature or waveform, which canbe an identification or fingerprint, that the network devices store fromthe UE devices as a time and frequency reference, as well as foridentification. Each waveform can be enumerated by the Physical CellIdentity (PCI). The network devices of the network environment 100 cancommunicate broadcasts with UE devices comprising a globally unique cellidentifier (CGI) as well and the network devices of the communicationenvironment 100 can utilize UE ANR functions, in which UE devices candecode and report CGI information of neighbor cells to the serving cellupon request.

For example, a network device such as a macro cell network device 102 or104 can maintain network data (e.g., an NRT) for each cell. The entriesor candidates of the network data can comprise data that the networkdevice utilizes about neighboring networks and network devices. Networkdevice 102, for example, can have a complete knowledge of its neighbors,such as of network device 104, 106, and 108. Network devices 104, 106and 108 can have a complete knowledge, an incomplete knowledge, or notbe aware of all neighbors depending upon inaccuracies in signalpropagation, maps data, or if a network has been newly installed.

In an example scenario, networks can service UE devices 110, 112, 114,116, and 118 through one of the macro network devices 102, 104, or othermicro access points 106, 108. As a UE device travels within the wirelesscommunications environment 100, the respective UE device can move in andout of the coverage area of the associated serving network device. Forexample, as a user is sending/receiving communications through theirrespective UE device, the user might be walking, riding in a car, ridingon a train, moving around a densely populated urban area (e.g., a largecity), wherein the movement might cause the mobile device to be movedamong various wireless communications networks. In such cases, it isbeneficial to route the network traffic (e.g., handoff) from a servingnetwork to a target network in order to continue the communication(e.g., avoid dropped calls). However, macro network devices 102, 104 canhave large network zones or coverage areas overlapping or with neighborrelations with micro cell network devices that are infrequently used andmanaged by the macro network devices 102 or 104, for example. If thesmall cell or micro network device neighbor relations are persistent innature, the neighbor lists in the NRT or other network data store can betruncated or can become too large to broadcast in a timely fashion. Thiscan prevent mobile stations or other network devices from identifyingsites or networks that are potential handover candidates, and adverselyaffect mobile handover performance.

In an aspect, infrequently-used, ephemeral or restricted access cells ornetwork devices that have had neighbor relations created via anautomated process such as ANR can be deleted after a relatively shortdelay of fixed, calculated, or operator settable duration with minimalimpact on performance and signaling load. For example, non-macro layers,such as the micro network devices 106, 108 can be removed from a networkdata in order to reduce impact and work with legacy macro systemscomprising the macro network devices 102, 104. Each macro eNB sectorcarrier or macro network device 102, 104 can support a limited number ofX2 neighbor relations, such as, for example, twenty-four neighborrelations of other network devices communicatively coupled to oneanother. This list of 24 neighbors can include all heterogeneous networklayers including macro network devices, Pico network devices, Femtonetwork devices and the like. From the micro network device perspective,a relatively large number of micro network devices (e.g., FAP devices)can have overlapping neighboring coverage with each corresponding macronetwork device (e.g., macro eNB sector carrier device). As active UE(in-call or communicating UEs) approach micro/macro coverage boundaries,the UE devices can detect and report new neighbor information (PCI). Ifthe detected PCI is not already populated as a neighbor in the data listor NRT, the macro cell devices and managing servers (e.g., eNB, FAPElemental Management System (EMS) and/or MME) can operate to exchangepertinent information to build an interface connection (e.g., an X2)link and pertinent neighbor list entries. A network device such as themanaging servers 130, 132 can operate to track the number of micronetwork device neighbors per macro network device, as part of ANRbehavior, which can continue until the macro neighbor list or networkdata is full and unable to comprise more neighbor relationships. If themacro neighbor list is full, for example, a new X2 and neighbor setupconnection will fail. This failure can operate as a trigger for themanaging server 130 or 132, as a Femto cell EMS to begin heterogeneousneighbor list management.

The managing server 130 or 132, for example, can determine the capacityfor neighbor relations for a macro neighbor list corresponding to aparticular network device (e.g., macro network device 102 or othernetwork device 104, 106, etc.) based on or in response to the failure toestablish a new network connection or neighbor setup. The failure, forexample, can indicate that the list, table or data tracking the neighborcandidates or entries is full, and the macro device 102 is not operableto establish further network relations. The failure can operate as atrigger event, in which the managing server or other network device(e.g., macro network device 102) maintaining the particular data set ofcandidate entries initiates management operations of the list. Thecapacity number can be determined according to the number of entries orpotential handover candidates populated in the list at the time of thefailure event. Alternatively or additionally, the capacity number can bebased on a statistical analysis of the number of failures occurring inthe list to establish a network connection and the number of entrieswithin the list or network data at those times. For example, an averagenumber based on a defined number of failure events over a period oftime, especially when failure instances could occur for one type ofnetwork relation, but not for others, for example.

In one embodiment, a network device (e.g., the managing server 120 orother network device) can determine a threshold number of micro networkdevices that are allowed to populate the list or network data for amacro network device (e.g., the particular macro network device 102) inresponse to the failure event or an analysis that a capacity number ofneighbor relations is being reached with greater frequency over a periodof time. The threshold number can be determined to be less than thecapacity number and also determined based on a number of macro networkdevices within the neighbor list for a particular time or time period,either before the failure trigger event or after. For example, thethreshold number of micro network devices allocated for neighbor entriesof the data can be based on a number of macro network devices within thenetwork data or list that the micro network devices have an overlappingcoverage zone with at the time of the failure trigger. The basis fordetermining the threshold number can be a one-to-one correspondence,another ratio, or a capacity for each macro network device of thenetwork data store being managed to establish neighbor relations withthe micro network devices, for example. The threshold number can be anumber that initiates other trigger events for further analysis of theneighbor relation data and be considered as a threshold trigger or asoft threshold number for the additional analysis of neighbor relationswithin the communication environment 100. For example, as new micronetwork devices are added, the threshold number could be crossed orexceeded, but not exceed the capacity number without a failure toestablish a network neighbor relation occurring or having a highprobability of occurring.

After a neighbor relation entry or the network data for handovercandidates exceeds the capacity number, further analysis of the networkdevices and statistical data corresponding to the different networkdevices within the network data as entries can be computed by themanaging server 120 or other network device, in which the network datais associated with for maintaining neighbor relations. For example,where a Femto network device keeps track of neighbor relations for eachmacro network device and the micro network devices, when the micronetwork devices cross the threshold number within the data list, theFemto network device can remove current micro network device candidatesor entries from the list based on the statistical analysis of thosecandidates.

For example, micro cell network devices can be ranked based on thenumber of attachment attempts by UE devices with respect to time orbased on rates of attachment attempts by UE devices over a period oftime from historical data collected. Different intervals of time couldbe considered and weighted, for example, based on a time of day, certaindays of the week, seasonal dates, or the like. Based on the rankings,the network data could have certain micro network devices dropped asviable neighbor relation candidates, and other or new network datarelations can be added for a network device attempting to establish as anetwork candidate. The neighbor relation data thus becomes dynamic andupdateable for each network device and corresponding neighbor relationswhen the list becomes overly large, and/or failure conditions operate astriggering events. Other examples and implementations are furtherdetailed below.

Referring now to FIG. 2, illustrated is an example, non-limitingwireless communications environment 200 in accordance with variousembodiments described. The wireless communications environment 200 caninclude a heterogeneous network environment that has a multitude ofwireless communications networks, each having a respective coveragearea. For example, a macro network device 204 facilitates a networkcoverage area or zone 206 that neighbors other coverage areas of macronetwork devices 212 and micro network devices 214. The coverage area ofsome of the wireless communications networks can overlap such that oneor more network devices can provide coverage areas or zones to UEs ormobile devices whose coverage areas from different networks of networkdevices overlap. For example, a relatively large number of FAP can haveoverlapping/neighboring coverage with each macro eNB sector carrier,such as with the macro network device 204. The network devices of theheterogeneous network environment can operate with one another as aSelf-Organizing Network (SON), in which at least some of the networkdevices can be configured to provide self-configuration andself-optimizing capabilities that provide the ability to automatecertain operations, management functions and system managementfunctions, such as in establishing network neighbor relations forpotential handover of the UE device 220.

A management server 202 is communicatively coupled to the macro networkdevice 204 and a network neighbor management component 210. Themanagement server 202 is configured to facilitate self-configuration,self-optimization, monitoring, and operation management to allow thenetwork devices to be communicatively coupled into the network andoperate with little to no human intervention without delay for potentialhandover within the SON network environment 200. The management server202 can be configured to communicate event data to the network neighbormanagement component 210. For example, the management server 202 canoperate to program and communicate trigger events to the networkneighbor management component 210. A trigger event can comprise, forexample, one or more events such as a failure of a network device (e.g.,a macro network device 212, a micro network device 214) to establish aneighbor relation entry or to establish an interface connection (e.g.,an X2 interface link) with the macro network device 204 or anothernetwork device. Although the network environment 200 is illustrated fora macro sector carrier (the macro network device 204), other networkdevices of the heterogeneous network could also be considered andincluded for neighbor relations management via the management server 202and the network neighbor management component 210.

Additional trigger events can comprise a number of entries in a networkdata 208 (e.g., a data store, candidate list, NRT, or the like)satisfying a threshold condition with a threshold (amount) number,and/or satisfying a defined amount of neighbor relation entries relativeto the threshold number. For example, a threshold number of networkdevice neighbor relations or handover candidates stored in the networkdata 208 can be set as a trigger. The trigger event can occur inresponse to the threshold condition being satisfied, such as meeting orexceeding a number of neighbor relations with macro network devices 212,micro network devices 214, a combination of macro and micro networkdevices in a particular ratio (e.g., 1 to 1, 2 to 1 or the like macro tomicro devices with neighbor relations), or thresholds correspondingrespectively to a determined number of macro network devices and micronetwork devices for established neighbor relations. The threshold numberor a defined number relative to the threshold number can be less thanthe capacity number. The defined number, for example, can be less thanthe threshold number, which can enable a reserve capacity with respectto macro network devices or specifically for micro network devices to beable to establish future neighbor relations and initiate neighborrelation management operations in response to a trigger event, forexample.

The threshold can be determined by the management server 202 and/or thenetwork neighbor management component 210. The threshold can comprise anumber of data entries or neighbor relations corresponding to macronetwork device neighbor relations and/or micro network device neighborrelations tracked with the data store 208. Additionally oralternatively, the threshold can be determined based on a capacity ofneighbor relations with respect to a network device, such as the macronetwork device 204, or, in other words, that are communicatively coupledto the macro network device 204, or with which the macro network device204 is potentially initialized or set up with for handover operations.For example, a capacity of neighbor relations for a macro sector carrieror macro network device 204 could be twenty-four entries, asillustrated. However, other capacities or numbers could also bedetermined based on a capacity of the network device (e.g., macronetwork device 204) to establish neighbor relations for potentialhandover candidates with the UE 220 from the network area 220. Forexample, the threshold number could be half the capacity number ofnetwork device neighbor relations entries or a number relative to thenumber of macro network device neighbor relations currently stored inthe data store 208. For example, the threshold number could bedetermined to be twelve micro network devices that the macro networkdevice 204 is operable to establish network neighbor relations with andperform handover operations for transfer of the UE device 220.

The threshold can comprise a number of micro cell network devices 214with neighbor relations, for example, that are determined based on anumber of macro network devices 212 with neighbor relation entriesstored within a period of time in the data store 208. For example,within an hour or other time period twelve macro network devices 214could have neighbor relations stored within the data store 208. As themicro network devices 214 overlap with or share boundaries with themacro network devices 212, the threshold number for neighbor relationswith micro network devices 214 can be determined to be ten or a numberthat is equal to or less than the number of macro network devices 212with neighbor relations already stored in the data store 208.Alternatively, the threshold number of neighbor relations for micronetwork devices 214 could be greater than the number of macro deviceneighbors tracked with the data store 208. The threshold numberdetermined can also be less than the capacity number without aprobability of failure occurring. Consequently, a trigger can includethe threshold number or threshold condition being satisfied, such as anumber of neighbor relations corresponding to the micro network devices212 exceeding or meeting the threshold number of relations designatedfor the micro network devices within the data store 208.

Further, the management server 202 is configured to determine a definednumber of neighbor relations for a particular type of network deviceoperating within the network environment 200, such as for micro networkdevices 214, which can include Femto cell devices, Pico cell devices,Metro cell devices, and the like. The defined number can be a numberthat defines a defined condition as a trigger event for initiatedmanagement operations for the neighbor relations and the data store 208,for example. The defined number can be defined specifically for allmicro cell network devices and corresponding neighboring networks thatare brought online or in communication with the network environment 200as potential neighbors for a particular macro network device (e.g.,204). The defined number can be determined to be equal to or less thanthe threshold number for a threshold condition. For example, thethreshold number can be determined to be twelve for Femto or micronetwork devices because twelve macro network devices 212 haveestablished neighbor relations that the micro network devices canoverlap with, and/or based on other factors, such as the capacity numberof network relations, as discussed above. In addition, the definednumber can be determined based on the threshold number, and bedetermined to be less than twelve, such as ten. In this example, asecond or additional trigger event can be a micro network device 214attempting to connect or establishing neighbor relations with the macrosector carrier or macro network device 204. In this case, the number ofmicro network devices 214 with neighbor relations in the data store 208becomes eleven and exceeds the defined number. The number does notexceed the threshold number or the capacity number for neighborrelations, but can further trigger management operations to ensure thatthe threshold is not exceeded.

In accordance with the above example, the network management component210 is configured to further analyze the data store and the statisticsof operation for the micro network devices 214. The network managementcomponent 210 operates to determine a statistical use of the micronetwork devices 214. A statistical profile can be generated and storedwithin the data store 208 corresponding to each one of the networkdevices. With regard to managing the micro network devices 214, astatistical average of attach attempts can be determined as a functionof an interval of time (e.g., the last hour from the initialization orsetup of the additional micro network device as a neighbor), provided aspart of the statistical profile. The number of attach attempts of UEdevice to the corresponding networks can be used to assess frequency ofuse, common travel paths, high usage for particular times, data periodsor time of the year with regard to seasonal use of the particularnetwork. Work hours or lunch hours in a day could prompt more use duringcertain other hours for UE devices to travel through, for example. Arate of attachment could be determined for each network device. As such,the network neighbor management component 210 can assess attach attemptrates of the micro network devices 214 that have establish neighborrelations.

In addition, UE device parameters can be also factored into thestatistical profile for potential handover candidates with other networkdevices, such as mobility, location, direction, speed, and the like, aswell as times and locations of the network devices or the networkenvironment 200 conditions for determining the priority of the micronetwork device and corresponding neighbor relations/connections. Forexample, where a new network device, such as a new micro network deviceis more active during a certain time of day, the time frame for analysisof the number of attach attempts could be delayed for the newly addedneighbor connection with the new micro network devices because themanagement server 202 or the network neighbor management component 210has ascertained this is a high activity time for this particular networkrelation compared to other times. Thus, maintaining the neighborrelations and connections for the newly joining or connection networkdevices would be more efficient event though previous times haveindicated little or no activity (e.g., attach attempts).

The network neighbor management component 210 is configured toprioritize and clean the network neighbor relations established andstored within the data store 208. The prioritization can be establishedbased on a rank of the micro network devices 214, which can increase ordecrease in rank based on the statistical profile. For example, themicro network device 218 can comprise a high rate of attempts per timeperiod (e.g., within an hour, time of day, or other set of time periodand dates). Conversely, the micro network device 216 has a number of lowattach attempts per time period. The network neighbor managementcomponent 210 can thus determine that micro network device 218 has ahigher rank or a higher priority than other micro network devices 214for maintaining neighbor relations or keeping a more permanent neighborrelation entry in the data store 208, for example, such as the micronetwork device 216. As a result, the network neighbor managementcomponent 210 is configured to delete or cancel the neighbor relation(e.g., an X2 interface link) corresponding to the micro network device216. The entry can be deleted or canceled from the data store 208 foridentifying the micro network device 216, such as with PCI or theneighbor information pertaining to the device 216. The network neighbormanagement component 210 is configured to prioritize and cleanup theneighbor relations and corresponding data in the data store in order todecrease the number of neighbor relation entries for the data store 208to a number of micro network cell devices to be at or below the definednumber. For example, where the defined number is ten micro networkdevices 214, and the number has increased beyond ten, the networkneighbor management component 210 operates to maintain the definednumber by prioritizing and removing micro network devices withestablished neighbor relations to satisfy the defined number for thedefined condition. Alternatively or additionally, the prioritization andremoval operations generated by the network neighbor managementcomponent 210 can be based on a tier of the statistical profile andranks. For example, a top tier of network devices and correspondingneighbor relations could be kept and a bottom tier could be removed bythe prioritization and cleanup (or removal) operations initiated by thenetwork neighbor management component 210. For example, the micronetwork devices having a low attach attempt rate, or low attach attemptsuccess rate, or an attach rate attempt that is below a bottom threshold(e.g., no attempts within a period of time, or equal to the attachattempt rate of the lowest micro network device 216) could be removed toallow for further periods of time between prioritization and cleanupoperations to be performed.

The management server 202 and the network neighbor management component210 are configured to dynamically determine the various conditions(e.g., the threshold condition, the capacity number, and/or the definedcondition and respective numbers) based on the changing conditions ofthe neighbor relations. For example, given the above example of FIG. 2,data store 208 can be expanded or decreased depending upon thedetermination of the threshold number for a threshold condition or theother conditions (e.g., capacity condition/number, and/or change in thedefined condition/number or success rate). When an increase in thenumber of macro network devices with neighbor relations for a given timeperiod occurs, the threshold number corresponding to the number micronetwork devices for neighbor relations could be changed, and thus, thedefined number operating a trigger for prioritization and cleanupoperations can also be re-assessed, or re-determined.

The network neighbor management component 210 can operate to analyze andmanage the entries of the data store 208 based on a period of time, atrigger event occurring or being communicated via the management server202, for example. In response to a trigger event, such as a failure of anetwork device establishing a neighbor relation or to be communicativelycoupled to the macro network device 204 via an entry in the data store208 or an interface connection failing to generate when a network deviceis detected, the network neighbor management component 210 can operateto determine data about the data store 208 for a determination of thecapacity number and a threshold number as another threshold event. Forexample, the network neighbor management component 210 can receive thefailure event trigger and initiate data analysis that determines anumber of macro network devices 212 with neighbor relation entries inthe data store, the number of micro network devices 214, and set acapacity number of total neighbor relation entries corresponding for thedata store 208 to store entries. The management server 202 can analyzethe data and determine a second threshold event in response based on thecapacity number for neighbor relations to be established and othercriteria discussed above such as a relative number of other networkdevices (e.g., macro network devices, micro network devices or othernetwork devices) that have established network neighbor relations (e.g.,X2 interface connections or some other interface link). The networkneighbor management component 210, the management server and/or themacro network device 204 can operate to determine and monitor the datastore 208 according to the threshold number determined as a secondtrigger mechanism. For example, the threshold number could be determinedto be twelve or a number less than the capacity number or number ofmacro network devices 212. The defined condition could be determined tobe less than the threshold number based on a defined interval forreserve, such as two less or less than two to enable other devices toestablish network relations and maintain greater dynamics inestablishing neighbor relations.

Consequently, the operations of the network environment 200 in aheterogeneous network of different macro and micro network devices withless coverage area, and/or overlapping the coverage zones of a macronetwork, provide an automated means to optimize large neighbor lists incomplex layered networks. Neighbors are maintained when/where neededmost, and removed when/where needed least. Mobility probability in a setof statistics or a statistical profile can be considered in the neighboroperations among the components/devices of the network to beforeneighbors and neighbor relations/connections (e.g., neighbor networksand corresponding network devices) are deleted. Thus, the risk of adelayed handover, neighbor list instability and associated signalingoverhead can be reduced.

Referring now to FIG. 3, illustrated is another example of theenvironment 200. A micro network 302 has newly established neighborconnections with the macro network device 204 and is operable as apotential handover candidate for the UE device 220. The managementserver 202 is configured to detect the new network neighbor connectionrelationship with the macro network device 204, for example, and entersthe data store 208 with the identifying information (e.g., PCI data orother identification data) to operate normal neighbor relationsautomatically, such as part of 3GPP ANR for LTE neighbors or for othernetwork types (e.g., 4GPP, Wi-Fi, etc.). The management server 202 canoperate to communicate a trigger event, in the case that a definednumber for a defined condition has been satisfied or met, such as whenthe number of micro network devices 214 with neighbor relationsestablished has exceed the defined number of ten, or some otherdetermined defined number.

The network neighbor management component 210 can operate in response tothe trigger event, such as the defined number being less than the numberof micro network devices neighbors that are set up or having interfaceconnections for potential handover candidates within the networkenvironment 200. In response to the trigger event, the network neighbormanagement component 210 can analyze the statistical or data of thestatistical profile and perform prioritization and cleanup of theneighbor relations and ANR data of the data store 208 as discussedabove.

Referring now to FIG. 4, illustrated is another example of the networkenvironment 200 in accordance with embodiments described. The networkneighbor management component 210 operates to resort the data of theneighbor relation statistics and determines different priorities basedon different statistics of attach attempts over one or more time periodsfor analysis. As described above, the network neighbor managementcomponent 210 can determine a statistical profile of the networksdevices, such as the micro network devices 214 that have initiated andestablished neighbor relations (e.g., X2 or other interface links) foreach macro network device, such as macro network device 204 or othernetwork devices.

The resorting operations of the network neighbor management component210 can result from the defined number (e.g., 10 according to the aboveexample) being exceeded or met based on a defined condition beingsatisfied. The result of resorting or prioritization operationsdetermines, for example, that the micro network device 402 has increasedin priority according to a different rank being determined from amongthe micro network devices 214. The statistical profile can comprise agraph or chart with respect to time or as a function of attach attemptclusters with respective dates, or other graphical analysis that isdynamic for the statistics of each micro network device. Thus, the micronetwork device 402 has been moved upward relative to the positionrepresented in FIGS. 2 and 3 of the example embodiments based on thechange in priority for handover operations with the UE device 220 orother UE device.

The network neighbor management component 210 can operate to cancel thelowest priority network devices, such as the micro network device 216.The network neighbor management component 210 can initiate cleanup atvarious times, and dynamically as network conditions or activity (e.g.,an increase in UE device data delivery or communications) increase. Thecleanup or removal of micro network devices, for example, can occur atthe instance of the defined number being exceeded or in a time framethereafter based on whether the newly added micro network device 302 isincluded in the analysis or not. When the micro network device 302 isincluded for cleanup, the prioritization operations can be initiatedafter UE device operations are not continued or ceased, or based on theprobability of handover according to the UE devices mobility at the timeof prioritization. Consequently, UE device parameters can be factoredinto the statistical profile for potential handover candidates withother network devices and removed accordingly.

Referring now to FIG. 5, illustrated is an example of network devicesoperable to manage neighbor relations corresponding to a networkcommunication environment of a heterogeneous network. A network 500comprises a network device 502 such as a Macro evolved NodeB device, aFemto cell network device or other network cell device that operates toprovide a coverage area for UE devices. The network device 502 comprisesa data store(s) 506, a Radio Resource Control (RRC) component 508, and anetwork neighbor management component 510.

The network device 502 can be communicatively coupled to managementserver 504 that can provide maintenance and operations control to thenetwork device, as well as ANR functions within 3GPP or other protocols.The data store 506 can operate as a NRT to store and maintain neighborentries for potential network neighbor candidates in a handoveroperation. The NRT entries can be managed or defined by the managementserver 504 when ANR or neighbor relations management component 510 isimplemented. However, base stations such as the network device 502 canbe launched without entries initially. Each NRT entry or neighborrelation/connection can be uniquely identified by a target cellidentifier. If the target cell is an LTE cell at the same frequency, theidentifier is the CGI, and NRT also contains the PCI. It is the CGI thatthe network device 502 uses when signaling to another network device viathe management server 504, since the management server 504 can routemessages based on network device identity which is a part of CGI. TheCGI is also used when acquiring the IP address of another networkdevice, which is used for X2 interface or another interface (e.g., S1)establishment. Additionally, the NRT entry contains information aboutthe interface connection availability, whether the network neighbormanagement component 510 can remove the neighbor relation, and whetherthe neighbor relation can be used for handover or not.

The network neighbor management component 510 can function toautomatically add and remove entries to/from NRT or data store 506.Additions are driven by the RRC component 508 signaling between thenetwork devices (e.g., macro or micro network devices) and mobiles,which provides measurement control and reporting means. The RRCcomponent can be used to define measurements of candidate cells, whichmeans that the mobiles or UE devices report measurement information tothe serving base station or network device 502, and upon request themobile also decodes and reports the unique CGI information.

In one embodiment, each network device 502 (e.g., macro eNB sectorcarrier) can support a limited number of X2 neighbor relations (e.g., acapacity number). For example, the figures discussed above used theexample of twenty-four entries, although other capacity numbers couldalso be functional depending upon the type of network device (e.g.,macro, micro, Wi-Fi etc.). This list or network data of 24 neighborsincludes all heterogeneous layers including macro, Pico, Femto etc. Fromthe Femto network device or other micro network device perspective, arelatively large number of FAP or micro network device access pointshave overlapping/neighboring coverage with each macro network device(e.g., a macro eNB sector carrier device. As active UE devices (in-callor communicating on the heterogeneous network) approach the macro/microcoverage boundaries they will detect and report new neighbor information(PCI). If the detected PCI is not already populated as a neighbor, themacro network device (e.g., eNB), the micro network device and/ormanagement server 504 can exchange pertinent information to build an X2link and pertinent neighbor list entries in the data store 506. Thenetwork neighbor management component 510 can be specific for each macroand/or micro network device (e.g., as a Femto element management server(EMS)) can operate to track the number of Femto neighbors per macronetwork device (e.g., per macro eNB sector carrier). The networkautomatic neighbor behavior can continue until the neighbor list isfull, such as with macro network device neighbor relation entries orcandidate entries. If the macro neighbor list is full, the new X2 andneighbor setup will fail. This failure is a trigger for the networkneighbor management component 510 (e.g., as Femto EMS) to beginheterogeneous network neighbor list management.

For example, assume the neighbor list maximum size (capacity number) istwenty-four and the ANR failure occurs for the thirteenth micro neighboraddition attempt. In this case the network neighbor management component510 can automatically determine that the maximum number of micro networkdevice neighbors is twelve or some other threshold number defined forthe micro network devices. The network neighbors can be dynamic, such asfor Macro LTE neighbors, and thus, the neighbors can be added andsubtracted as coverage and user distribution change. The networkneighbor management component 510 or the management server 504 willoccasionally or at defined intervals re-test limits beyond twelve micronetwork device neighbors, but the limit is assumed to be twelve forillustration.

Macro ANR neighbor additions, for example, can be relatively fast, butremovals can be relatively slow. Thus, it can be impractical to removeneighbors fast enough to support fast additions when the neighbor listis otherwise full. For this reason the network neighbor managementcomponent 510 can maintain at least one empty neighbor list position (inthis case 2) to allow for rapid neighbor addition before neighborre-sorting and cleanup. In this case the maintained micro network deviceneighbor list size is ten as a defined number relative to the thresholdnumber.

As active UE (in-call) approach Micro/Macro network device coverageboundaries they will detect and report new neighbor information (PCI).If the detected PCI is not already populated as a neighbor, the devicesand components of the network will exchange pertinent information tobuild an X2 link or other interface connection and pertinent neighborlist entries are populated in the data store 506. This activity canresult in a successful handover from macro network devices (e.g., amacro LTE sector carrier) to micro network devices (e.g., a Femtonetwork device). The network neighbor management component 510 isconfigured to update the number of micro network device neighbors permacro network device. In this case the number of micro neighbors hasincreased from ten to eleven, which is beyond the maintained micronetwork device neighbor list size (threshold number).

The network neighbor management component 510 can operate to be able todetect and remember the number and rate of attach attempts from nearbyUE devices. This is an indication of the number of nearby users andtheir mobility. This is also an indication of the probability of moreincoming handover attempts. That is, in cases where more nearby UEdevice attempt exists to attach to the micro network device then thereis a higher probability that at least one nearby UE device shall requirehandover to the micro network device. Ideally existing neighborrelations are in place before the handover is needed, but notnecessarily. Micro network devices with a high rate of attach attemptstherefore require more permanent neighbor relations than micro networkdevices with a low rate of attach attempts. This therefore can reducethe need to repeatedly add and delete the same neighbor relation. Micronetwork devices with a low rate of attach attempts likely will notexperience handover with a macro network device any time soon. Removingthese neighbors quickly leaves neighbor list room and time for othermicro network devices in a more active a dynamic network environment.For these reasons, the micro network neighbors (towards a specific macrosector carrier) are ranked according to the rate of attach attempts. Ifnecessary to remove neighbors to stay within the maintained micronetwork neighbor list size (the defined number), micro network deviceswith a low rate of attach attempts are removed first. Micro networkdevice neighbor lists are constantly re-sorted as new neighbors areadded and deleted. Micro network device neighbor lists also expand orcontract according to the detection mechanisms discussed above.According to the prior example, the eleventh Femto neighbor was added.Next the Femto neighbor list is resorted according to the rate of attachattempts. Finally the eleventh Femto neighbor (at bottom of thelist=lowest rate of attach attempts) can be removed by the networkneighbor management component 510, for example. This clears space fornew neighbors to be quickly added to the Micro/Macro neighbor list asrequired. An advantage of these operations is that it enablesheterogeneous networks to proactively adapt to dynamic neighborscenarios typical for heterogeneous service areas.

While the methods described within this disclosure are illustrated inand described herein as a series of acts or events, it will beappreciated that the illustrated ordering of such acts or events are notto be interpreted in a limiting sense. For example, some acts may occurin different orders and/or concurrently with other acts or events apartfrom those illustrated and/or described herein. In addition, not allillustrated acts may be required to implement one or more aspects orembodiments of the description herein. Further, one or more of the actsdepicted herein may be carried out in one or more separate acts and/orphases. Reference may be made to the figures described above for ease ofdescription. However, the methods are not limited to any particularembodiment or example provided within this disclosure and can be appliedto any of the systems disclosed herein.

FIG. 6 illustrates an example, non-limiting method 600 for managingneighbor relations, according to an aspect. At 602, a failure toestablish a network connection with a network device of a heterogeneousnetwork is detected. The failure, for example, can be a failure of anetwork neighbor relation to be ascertained such as via an X2 interfaceconnection or other interface link with neighboring network devices fora potential handover for a UE device in the heterogeneous network. At604, in response to the detected failure, a capacity number of networkconnections (e.g., neighbor relations or interface link connections) isdetected with which the network device is operable to establish with aset of macro cell network devices and a set of micro cell networkdevices.

At 606, a determination is made of a threshold number of micro cellnetwork devices with which the network device is operable to establishthe network connection. For example, determining the threshold number ofmicro cell network devices can be based on the number of micro cellnetwork devices corresponding to macro cell network devices that havenetwork connections to the network device and the capacity number ofnetwork connections detected.

At 608 a determination is made of a defined number of micro cell networkdevices that is less than the threshold number of micro cell networkdevices with which the network device is operable to establish thenetwork connection.

At 610, an additional network connection is facilitated with anadditional micro network device to the network device that causes anumber of micro cell network devices connected to the network device tobe greater than the defined number of micro cell network devices.

In one embodiment, the method 600 can comprise determining, by thedevice, a number of connection attempts to the set of micro cell networkdevices. In addition, a rate of connection attempts to the set of microcell network devices. The set of micro cell network devices can beranked based on the rate of connection attempts to the set of micro cellnetwork devices. In response to the number of micro cell network devicescommunicatively connected to the network device being determined to begreater than the defined number of micro cell network devices, at leastone network connection of at least one micro cell network device to thenetwork device can be removed based on the number of attach attempts orthe rate of connection attempts to one or more micro cell networkdevices.

The method 600 can further comprise modifying the threshold number ofmicro cell network devices based on a change in a number of macro cellnetwork devices or micro cell network devices connected to the networkdevice such as by neighbor relations or neighbor interface links forpotential handover candidates.

FIG. 7 illustrates an example, non-limiting method 700, according to anaspect. At 702, the method 700 comprises generating network neighbordevice data of a set of macro network devices comprising macro coveragezones and a set of micro network devices comprising micro coverage zonesthat overlap with the macro coverage zones, wherein the set of micronetwork devices and the set of macro network devices are communicativelycoupled to a macro network device of a heterogeneous network.

At 704, a failure of a macro network device to establish a networkconnection (e.g., a neighbor relation interface link) with a networkdevice (a macro network device or a micro network device).

At 706, in response to detecting a failure of the macro network deviceto establish a network connection with a network device, a capacitynumber of network connections with the macro network device isdetermined based on the network neighbor device data, such as neighborrelation entries or connections. At 708, a threshold number isdetermined from the network neighbor device data. The network neighbordevice data represents, for example, the set of micro network deviceswith which the macro network device is operable to establish the networkconnection based on the capacity number of network connections and anumber of macro network devices of the set of macro network devices.

At 710, defined number of micro network devices that is less than thethreshold number of the network neighbor device data is maintained.Maintaining the defined number of micro network devices that is lessthan the threshold number of the network device data can furthercomprise facilitating the network connection with an additional micronetwork device. The number of the set of micro network devices inconnection with the macro network device can also be greater than thedefined number of micro network devices. Maintaining the defined numberof micro network devices that is less than the threshold number of thenetwork device data can further comprise generating a rank of the set ofmicro network devices based on an attach attempt rate, and removing thenetwork connection of at least one micro network device to the macronetwork device based on the rank.

In one embodiment, the method 700 can comprise modifying the thresholdnumber in response to an additional macro network device of the set ofmacro network devices being determined to have established the networkconnection (neighbor relation link) with the macro network device forpotential handover with a UE device. In addition or alternatively, thethreshold number can be modified in response to at least one macronetwork device of the set of macro network devices being determined tohave been removed from the network connection with the macro networkdevice.

FIG. 8 illustrates another example, non-limiting embodiment of a processflow 800. At 802, network neighbor device data is generated thatrepresents micro network device candidates that neighbor a macro networkdevice in a heterogeneous network comprising micro network devices andmacro network devices for a potential transfer from the macro networkdevice.

At 804, determining a threshold number of micro network devices withwhich the macro network device is operable to establish a neighborrelation is determined. The determining the threshold number of micronetwork devices can be initiated in response to a failure to establishthe neighbor relation with the additional micro network device.

At 806, a defined size of the network neighbor device data representingthe micro network device candidates that is less than the thresholdnumber of micro network devices with which the macro network device isoperable to establish the neighbor relation is maintained. Themaintaining the defined size of the network neighbor device data cancomprise generating a priority of the micro network device candidates ofthe network neighbor device data, and removing at least one micronetwork device candidate from the network neighbor device data based onthe priority, which can be in response to the facilitating theadditional neighbor relation with the additional micro network device.

At 808, an additional neighbor relation is facilitated with anadditional micro network device that is detected within theheterogeneous network, and not already included in the threshold numberof micro network devices.

By way of further description with respect to one or more non-limitingways to facilitate network traffic routing selection, FIG. 9 is aschematic example wireless environment 900 that can operate inaccordance with aspects described herein. In particular, examplewireless environment 900 illustrates a set of wireless network macrocells. Three coverage macro cells 902, 904, and 906 include theillustrative wireless environment; however, it is noted that wirelesscellular network deployments can encompass any number of macro cells.Coverage macro cells 902, 904, and 906 are illustrated as hexagons;however, coverage cells can adopt other geometries generally dictated bya deployment configuration or floor plan, geographic areas to becovered, and so on. Each macro cell 902, 904, and 906 is sectorized in a2π/3 configuration in which each macro cell includes three sectors,demarcated with dashed lines in FIG. 9. It is noted that othersectorizations are possible, and aspects or features of the disclosedsubject matter can be exploited regardless of type of sectorization.Macro cells 902, 904, and 906 are served respectively through basestations or eNodeBs 908, 910, and 912. Any two eNodeBs can be consideredan eNodeB site pair. It is noted that radio component(s) arefunctionally coupled through links such as cables (e.g., RF andmicrowave coaxial lines), ports, switches, connectors, and the like, toa set of one or more antennas that transmit and receive wireless signals(not illustrated). It is noted that a radio network controller (notshown), which can be a part of mobile network platform(s) 914, and setof base stations (e.g., eNode B 908, 910, and 912) that serve a set ofmacro cells; electronic circuitry or components associated with the basestations in the set of base stations; a set of respective wireless links(e.g., links 916, 918, and 920) operated in accordance to a radiotechnology through the base stations, form a macro radio access network.It is further noted that, based on network features, the radiocontroller can be distributed among the set of base stations orassociated radio equipment. In an aspect, for universal mobiletelecommunication system-based networks, wireless links 916, 918, and920 embody a Uu interface (universal mobile telecommunication system AirInterface).

Mobile network platform(s) 914 facilitates circuit switched-based (e.g.,voice and data) and packet-switched (e.g., Internet protocol, framerelay, or asynchronous transfer mode) traffic and signaling generation,as well as delivery and reception for networked telecommunication, inaccordance with various radio technologies for disparate markets.Telecommunication is based at least in part on standardized protocolsfor communication determined by a radio technology utilized forcommunication. In addition, telecommunication can exploit variousfrequency bands, or carriers, which include any electromagneticfrequency bands licensed by the service provider network 922 (e.g.,personal communication services, advanced wireless services, generalwireless communications service, and so forth), and any unlicensedfrequency bands currently available for telecommunication (e.g., the 2.4GHz industrial, medical and scientific band or one or more of the 5 GHzset of bands). In addition, mobile network platform(s) 914 can controland manage base stations 908, 910, and 912 and radio component(s)associated thereof, in disparate macro cells 902, 904, and 906 by wayof, for example, a wireless network management component (e.g., radionetwork controller(s), cellular gateway node(s), etc.). Moreover,wireless network platform(s) can integrate disparate networks (e.g.,Wi-Fi network(s), Femto cell network(s), broadband network(s), servicenetwork(s), enterprise network(s), and so on). In cellular wirelesstechnologies (e.g., third generation partnership project universalmobile telecommunication system, global system for mobile communication,mobile network platform 914 can be embodied in the service providernetwork 922.

In addition, wireless backhaul link(s) 924 can include wired linkcomponents such as T1/E1 phone line; T3/DS3 line, a digital subscriberline either synchronous or asynchronous; an asymmetric digitalsubscriber line; an optical fiber backbone; a coaxial cable, etc.; andwireless link components such as line-of-sight or non-line-of-sightlinks which can include terrestrial air-interfaces or deep space links(e.g., satellite communication links for navigation). In an aspect, foruniversal mobile telecommunication system-based networks, wirelessbackhaul link(s) 924 embodies IuB interface.

It is noted that while exemplary wireless environment 900 is illustratedfor macro cells and macro base stations, aspects, features andadvantages of the disclosed subject matter can be implemented in microcells, pico cells, Femto cells, or the like, wherein base stations areembodied in home-based equipment related to access to a network.

To provide further context for various aspects of the disclosed subjectmatter, FIG. 10 illustrates a block diagram of an embodiment of accessequipment and/or software 1000 related to access of a network (e.g.,base station, wireless access point, Femtocell access point, and soforth) that can enable and/or exploit features or aspects of thedisclosed aspects.

Access equipment and/or software 1000 related to access of a network canreceive and transmit signal(s) from and to wireless devices, wirelessports, wireless routers, etc. through segments 1002 ₁-1002 _(B) (B is apositive integer). Segments 1002 ₁-1002 _(B) can be internal and/orexternal to access equipment and/or software 1000 related to access of anetwork, and can be controlled by a monitor component 1004 and anantenna component 1006. Monitor component 1004 and antenna component1006 can couple to communication platform 1008, which can includeelectronic components and associated circuitry that provide forprocessing and manipulation of received signal(s) and other signal(s) tobe transmitted.

In an aspect, communication platform 1008 includes areceiver/transmitter 1010 that can convert analog signals to digitalsignals upon reception of the analog signals, and can convert digitalsignals to analog signals upon transmission. In addition,receiver/transmitter 1010 can divide a single data stream into multiple,parallel data streams, or perform the reciprocal operation. Coupled toreceiver/transmitter 1010 can be a multiplexer/demultiplexer 1012 thatcan facilitate manipulation of signals in time and frequency space.Multiplexer/demultiplexer 1012 can multiplex information (data/trafficand control/signaling) according to various multiplexing schemes such astime division multiplexing, frequency division multiplexing, orthogonalfrequency division multiplexing, code division multiplexing, spacedivision multiplexing. In addition, multiplexer/demultiplexer component1012 can scramble and spread information (e.g., codes, according tosubstantially any code known in the art, such as Hadamard-Walsh codes,Baker codes, Kasami codes, polyphase codes, and so forth).

A modulator/demodulator 1014 is also a part of communication platform1008, and can modulate information according to multiple modulationtechniques, such as frequency modulation, amplitude modulation (e.g.,M-ary quadrature amplitude modulation, with M a positive integer);phase-shift keying; and so forth).

Access equipment and/or software 1000 related to access of a networkalso includes a processor 1016 configured to confer, at least in part,functionality to substantially any electronic component in accessequipment and/or software 1000. In particular, processor 1016 canfacilitate configuration of access equipment and/or software 1000through, for example, monitor component 1004, antenna component 1006,and one or more components therein. Additionally, access equipmentand/or software 1000 can include display interface 1018, which candisplay functions that control functionality of access equipment and/orsoftware 1000, or reveal operation conditions thereof. In addition,display interface 1018 can include a screen to convey information to anend user. In an aspect, display interface 1018 can be a liquid crystaldisplay, a plasma panel, a monolithic thin-film based electrochromicdisplay, and so on. Moreover, display interface 1018 can include acomponent (e.g., speaker) that facilitates communication of auralindicia, which can also be employed in connection with messages thatconvey operational instructions to an end user. Display interface 1018can also facilitate data entry (e.g., through a linked keypad or throughtouch gestures), which can cause access equipment and/or software 1000to receive external commands (e.g., restart operation).

Broadband network interface 1020 facilitates connection of accessequipment and/or software 1000 to a service provider network (not shown)that can include one or more cellular technologies (e.g., thirdgeneration partnership project universal mobile telecommunicationsystem, global system for mobile communication, and so on) throughbackhaul link(s) (not shown), which enable incoming and outgoing dataflow. Broadband network interface 1020 can be internal or external toaccess equipment and/or software 1000, and can utilize display interface1018 for end-user interaction and status information delivery.

Processor 1016 can be functionally connected to communication platform1008 and can facilitate operations on data (e.g., symbols, bits, orchips) for multiplexing/demultiplexing, such as effecting direct andinverse fast Fourier transforms, selection of modulation rates,selection of data packet formats, inter-packet times, and so on.Moreover, processor 1016 can be functionally connected, through data,system, or an address bus 1022, to display interface 1018 and broadbandnetwork interface 1020, to confer, at least in part, functionality toeach of such components.

In access equipment and/or software 1000, memory 1024 can retainlocation and/or coverage area (e.g., macro sector, identifier(s)) accesslist(s) that authorize access to wireless coverage through accessequipment and/or software 1000, sector intelligence that can includeranking of coverage areas in the wireless environment of accessequipment and/or software 1000, radio link quality and strengthassociated therewith, or the like. Memory 1024 also can store datastructures, code instructions and program modules, system or deviceinformation, code sequences for scrambling, spreading and pilottransmission, access point configuration, and so on. Processor 1016 canbe coupled (e.g., through a memory bus), to memory 1024 in order tostore and retrieve information used to operate and/or conferfunctionality to the components, platform, and interface that residewithin access equipment and/or software 1000.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or deviceincluding, but not limited to including, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit, a digital signalprocessor, a field programmable gate array, a programmable logiccontroller, a complex programmable logic device, a discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions and/or processes describedherein. Processors can exploit nano-scale architectures such as, but notlimited to, molecular and quantum-dot based transistors, switches andgates, in order to optimize space usage or enhance performance of mobiledevices. A processor may also be implemented as a combination ofcomputing processing units.

In the subject specification, terms such as “store,” “data store,” datastorage,” “database,” and substantially any other information storagecomponent relevant to operation and functionality of a component and/orprocess, refer to “memory components,” or entities embodied in a“memory,” or components including the memory. It is noted that thememory components described herein can be either volatile memory ornonvolatile memory, or can include both volatile and nonvolatile memory.

By way of illustration, and not limitation, nonvolatile memory, forexample, can be included in memory 1024, non-volatile memory (seebelow), disk storage (see below), and memory storage (see below).Further, nonvolatile memory can be included in read only memory,programmable read only memory, electrically programmable read onlymemory, electrically erasable programmable read only memory, or flashmemory. Volatile memory can include random access memory, which acts asexternal cache memory. By way of illustration and not limitation, randomaccess memory is available in many forms such as synchronous randomaccess memory, dynamic random access memory, synchronous dynamic randomaccess memory, double data rate synchronous dynamic random accessmemory, enhanced synchronous dynamic random access memory, Synchlinkdynamic random access memory, and direct Rambus random access memory.Additionally, the disclosed memory components of systems or methodsherein are intended to include, without being limited to including,these and any other suitable types of memory.

In order to provide a context for the various aspects of the disclosedsubject matter, FIG. 11, and the following discussion, are intended toprovide a brief, general description of a suitable environment in whichthe various aspects of the disclosed subject matter can be implemented.While the subject matter has been described above in the general contextof computer-executable instructions of a computer program that runs on acomputer and/or computers, those skilled in the art will recognize thatthe various aspects also can be implemented in combination with otherprogram modules. Generally, program modules include routines, programs,components, data structures, etc. that performs particular tasks and/orimplement particular abstract data types. For example, in memory (suchas at least one memory) there can be software, which can instruct aprocessor (such as at least one processor 204) to perform variousactions. The processor can be configured to execute the instructions inorder to implement the analysis of monitoring an uplink power level,detecting the uplink power level is at or above a threshold level,and/or disable transmission of at least one message as a result of themonitored uplink power level.

Moreover, those skilled in the art will understand that the variousaspects can be practiced with other computer system configurations,including single-processor or multiprocessor computer systems,mini-computing devices, mainframe computers, as well as personalcomputers, base stations hand-held computing devices or user equipment,such as a tablet, phone, watch, and so forth, processor-basedcomputers/systems, microprocessor-based or programmable consumer orindustrial electronics, and the like. The illustrated aspects can alsobe practiced in distributed computing environments where tasks areperformed by remote processing devices that are linked through acommunications network; however, some if not all aspects of the subjectdisclosure can be practiced on stand-alone computers. In a distributedcomputing environment, program modules can be located in both local andremote memory storage devices.

With reference to FIG. 11, a block diagram of a computing system 1100operable to execute the disclosed systems and methods is illustrated, inaccordance with an embodiment. Computer 1102 includes a processing unit1104, a system memory 1106, and a system bus 1108. System bus 1108couples system components including, but not limited to, system memory1106 to processing unit 1104. Processing unit 1104 can be any of variousavailable processors. Dual microprocessors and other multiprocessorarchitectures also can be employed as processing unit 1104.

System bus 1108 can be any of several types of bus structure(s)including a memory bus or a memory controller, a peripheral bus or anexternal bus, and/or a local bus using any variety of available busarchitectures including, but not limited to, industrial standardarchitecture, micro-channel architecture, extended industrial standardarchitecture, intelligent drive electronics, video electronics standardsassociation local bus, peripheral component interconnect, card bus,universal serial bus, advanced graphics port, personal computer memorycard international association bus, Firewire and small computer systemsinterface.

System memory 1106 includes volatile memory 1110 and nonvolatile memory1112. A basic input/output system, containing routines to transferinformation between elements within computer 1102, such as duringstart-up, can be stored in nonvolatile memory 1112. By way ofillustration, and not limitation, nonvolatile memory 1112 can includeread only memory, programmable read only memory, electricallyprogrammable read only memory, electrically erasable programmable readonly memory, or flash memory. Volatile memory 1110 can include randomaccess memory, which acts as external cache memory. By way ofillustration and not limitation, random access memory is available inmany forms such as dynamic random access memory, synchronous randomaccess memory, synchronous dynamic random access memory, double datarate synchronous dynamic random access memory, enhanced synchronousdynamic random access memory, Synchlink dynamic random access memory,and direct Rambus random access memory, direct Rambus dynamic randomaccess memory, and Rambus dynamic random access memory.

Computer 1102 also includes removable/non-removable,volatile/non-volatile computer storage media. In an implementation,provided is a non-transitory or tangible computer-readable mediumstoring executable instructions that, in response to execution, cause asystem comprising a processor to perform operations. The operations caninclude comparing a first network congestion condition and a firstnetwork parameter condition received from a first set of network devicesof a first network, and a second network congestion condition and asecond network parameter condition received from a second set of networkdevices of a second network to a usage parameter and a movementparameter of a mobile device. The operations can also includedetermining a radio technology (e.g., radio network device) to which toroute network traffic of the mobile device. Determining the routing ofthe network traffic can include, based on a first outcome of thecomparing, determining to route the network traffic to the first set ofnetwork devices associated with a first radio technology. In anotherexample, determining the routing of the network traffic can include,based on a second outcome of the comparing, determining to route thenetwork traffic of the mobile device to the second set of networkdevices associated with a second radio technology. In an implementation,determining the set of network devices can include complying with anetwork selection policy received from a network device that provides aservice to the mobile device. Further, the operations can includefacilitating routing of the network traffic of the mobile device to theset of network devices.

In an implementation, the operations can include analyzing relativemovement of the mobile device with respect to the first set of networkdevices and the second set of network devices. According to anotherimplementation, the operations can include determining speed datarepresenting a substantially current speed of the mobile device anddirection data representing a substantially current direction of themobile device.

FIG. 11 illustrates, for example, disk storage 1114. Disk storage 1114includes, but is not limited to, devices such as a magnetic disk drive,floppy disk drive, tape drive, external or internal removable storagedrives, super disk drive, flash memory card, or memory stick. Inaddition, disk storage 1114 can include storage media separately or incombination with other storage media including, but not limited to, anoptical disk drive such as a compact disk read only memory device,compact disk recordable drive, compact disk rewritable drive or adigital versatile disk read only memory drive. To facilitate connectionof the disk storage 1114 to system bus 1108, a removable ornon-removable interface is typically used, such as interface component1116.

It is to be noted that FIG. 11 describes software that acts as anintermediary between users and computer resources described in suitableoperating environment. Such software includes an operating system 1118.Operating system 1118, which can be stored on disk storage 1114, acts tocontrol and allocate resources of computer system 1102. Systemapplications 1120 can take advantage of the management of resources byoperating system 1118 through program modules 1122 and program data 1124stored either in system memory 1106 or on disk storage 1114. It is to beunderstood that the disclosed subject matter can be implemented withvarious operating systems or combinations of operating systems.

A user can enter commands or information, for example through interfacecomponent 1116, into computer system 1102 through input device(s) 1126.Input devices 1126 include, but are not limited to, a pointing devicesuch as a mouse, trackball, stylus, touch pad, keyboard, microphone,joystick, game pad, satellite dish, scanner, TV tuner card, digitalcamera, digital video camera, web camera, and the like. These and otherinput devices connect to processing unit 1104 through system bus 1108through interface port(s) 1128. Interface port(s) 1128 include, forexample, a serial port, a parallel port, a game port, and a universalserial bus. Output device(s) 1130 use some of the same type of ports asinput device(s) 1126.

Thus, for example, a universal serial bus port can be used to provideinput to computer 1102 and to output information from computer 1102 toan output device 1130. Output adapter 1132 is provided to illustratethat there are some output devices 1130, such as monitors, speakers, andprinters, among other output devices 1130, which use special adapters.Output adapters 1132 include, by way of illustration and not limitation,video and sound cards that provide means of connection between outputdevice 1130 and system bus 1108. It is also noted that other devicesand/or systems of devices provide both input and output capabilitiessuch as remote computer(s) 1134.

Computer 1102 can operate in a networked environment using logicalconnections to one or more remote computers, such as remote computer(s)1134. Remote computer(s) 1134 can be a personal computer, a server, arouter, a network computer, a workstation, a microprocessor basedappliance, a peer device, or other common network node and the like, andtypically includes many or all of the elements described relative tocomputer 1102.

For purposes of brevity, only one memory storage device 1136 isillustrated with remote computer(s) 1134. Remote computer(s) 1134 islogically connected to computer 1102 through a network interface 1138and then physically connected through communication connection 1140.Network interface 1138 encompasses wire and/or wireless communicationnetworks such as local area networks and wide area networks. Local areanetwork technologies include fiber distributed data interface, copperdistributed data interface, Ethernet, token ring and the like. Wide areanetwork technologies include, but are not limited to, point-to-pointlinks, circuit switching networks, such as integrated services digitalnetworks and variations thereon, packet switching networks, and digitalsubscriber lines.

Communication connection(s) 1140 refer(s) to hardware/software employedto connect network interface 1138 to system bus 1108. Whilecommunication connection 1140 is shown for illustrative clarity insidecomputer 1102, it can also be external to computer 1102. Thehardware/software for connection to network interface 1138 can include,for example, internal and external technologies such as modems,including regular telephone grade modems, cable modems and DSL modems,ISDN adapters, and Ethernet cards.

It is to be noted that aspects, features, or advantages of the aspectsdescribed in the subject specification can be exploited in substantiallyany communication technology. For example, 4G technologies, Wi-Fi,worldwide interoperability for microwave access, Enhanced gatewaygeneral packet radio service, third generation partnership project LTE,third generation partnership project 2 ultra-mobile broadband, thirdgeneration partnership project universal mobile telecommunicationsystem, high speed packet access, high-speed downlink packet access,high-speed uplink packet access, global system for mobile communicationedge radio access network, universal mobile telecommunication systemterrestrial radio access network, LTE advanced. Additionally,substantially all aspects disclosed herein can be exploited in legacytelecommunication technologies; e.g., global system for mobilecommunication. In addition, mobile as well non-mobile networks (e.g.,Internet, data service network such as Internet protocol television) canexploit aspect or features described herein.

Various aspects or features described herein can be implemented as amethod, apparatus, or article of manufacture using standard programmingand/or engineering techniques. In addition, various aspects disclosed inthe subject specification can also be implemented through programmodules stored in a memory and executed by a processor, or othercombination of hardware and software, or hardware and firmware.

Other combinations of hardware and software or hardware and firmware canenable or implement aspects described herein, including the disclosedmethod(s). The term “article of manufacture” as used herein is intendedto encompass a computer program accessible from any computer-readabledevice, carrier, or media. For example, computer readable media caninclude but are not limited to magnetic storage devices (e.g., harddisk, floppy disk, magnetic strips . . . ), optical discs (e.g., compactdisc, digital versatile disc, blu-ray disc . . . ), smart cards, andflash memory devices (e.g., card, stick, key drive . . . ).

Computing devices typically include a variety of media, which caninclude computer-readable storage media or communications media, whichtwo terms are used herein differently from one another as follows.

Computer-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media can include,but are not limited to, random access memory, read only memory,electrically erasable programmable read only memory, flash memory orother memory technology, compact disk read only memory, digitalversatile disk or other optical disk storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or other tangible and/or non-transitory media which can be used to storedesired information. Computer-readable storage media can be accessed byone or more local or remote computing devices, e.g., via accessrequests, queries or other data retrieval protocols, for a variety ofoperations with respect to the information stored by the medium.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and includes any information deliveryor transport media. The term “modulated data signal” or signals refersto a signal that has one or more of its characteristics set or changedin such a manner as to encode information in one or more signals. By wayof example, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

What has been described above includes examples of systems and methodsthat provide advantages of the one or more aspects. It is, of course,not possible to describe every conceivable combination of components ormethods for purposes of describing the aspects, but one of ordinaryskill in the art may recognize that many further combinations andpermutations of the claimed subject matter are possible. Furthermore, tothe extent that the terms “includes,” “has,” “possesses,” and the likeare used in the detailed description, claims, appendices and drawingssuch terms are intended to be inclusive in a manner similar to the term“comprising” as “comprising” is interpreted when employed as atransitional word in a claim.

As used in this application, the terms “component,” “system,” and thelike are intended to refer to a computer-related entity or an entityrelated to an operational apparatus with one or more specificfunctionalities, wherein the entity can be either hardware, acombination of hardware and software, software, or software inexecution. As an example, a component may be, but is not limited tobeing, a process running on a processor, a processor, an object, anexecutable, a thread of execution, computer-executable instructions, aprogram, and/or a computer. By way of illustration, both an applicationrunning on a server or network controller, and the server or networkcontroller can be a component. One or more components may reside withina process and/or thread of execution and a component may be localized onone computer and/or distributed between two or more computers. Also,these components can execute from various computer readable media havingvarious data structures stored thereon. The components may communicatevia local and/or remote processes such as in accordance with a signalhaving one or more data packets (e.g., data from one componentinteracting with another component in a local system, distributedsystem, and/or across a network such as the Internet with other systemsvia the signal). As another example, a component can be an apparatuswith specific functionality provided by mechanical parts operated byelectric or electronic circuitry, which is operated by a software, orfirmware application executed by a processor, wherein the processor canbe internal or external to the apparatus and executes at least a part ofthe software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can include a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components. As further yet another example, interface(s) caninclude input/output components as well as associated processor,application, or application programming interface components.

The term “set”, “subset”, or the like as employed herein excludes theempty set (e.g., the set with no elements therein). Thus, a “set”,“subset”, or the like includes one or more elements or periods, forexample. As an illustration, a set of periods includes one or moreperiods; a set of transmissions includes one or more transmissions; aset of resources includes one or more resources; a set of messagesincludes one or more messages, and so forth.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

What is claimed is:
 1. A method, comprising: receiving, by a devicecomprising a processor, a communication indicating a failure toestablish a network connection with a network device of a heterogeneousnetwork; detecting, by the device in response to the receiving thecommunication, a capacity number of network connections with which thenetwork device is operable to establish with a set of macro cell networkdevices and a set of micro cell network devices; determining, by thedevice in response to the receiving the communication, a thresholdnumber of micro cell network devices with which the network device isoperable to establish the network connection; determining, by the devicein response to the receiving the communication, a defined number ofmicro cell network devices that is less than the threshold number ofmicro cell network devices with which the network device is operable toestablish the network connection; and facilitating, by the device inresponse to the receiving the communication, an additional networkconnection with an additional micro network device to the network devicethat causes a number of micro cell network devices connected to thenetwork device to be greater than the defined number of micro cellnetwork devices.
 2. The method of claim 1, wherein the determining thethreshold number of micro cell network devices is based on a number ofmacro cell network devices connected to the network device and thecapacity number of the network connections.
 3. The method of claim 1,further comprising: determining, by the device, a number of connectionattempts to the set of micro cell network devices; and determining, bythe device, a rate of connection attempts to the set of micro cellnetwork devices.
 4. The method of claim 3, further comprising: inresponse to the number of micro cell network devices communicativelyconnected to the network device being determined to be greater than thedefined number of micro cell network devices, removing, by the device,at least one network connection of at least one micro cell networkdevice to the network device based on the rate of connection attempts tothe set of micro cell network devices.
 5. The method of claim 3, furthercomprising: ranking, by the device, the set of micro cell networkdevices based on the rate of connection attempts to the set of microcell network devices.
 6. The method of claim 1, wherein the thresholdnumber of micro cell network devices is less than the capacity number ofthe network connections.
 7. The method of claim 1, further comprising:modifying, by the device, the threshold number of micro cell networkdevices based on a change in a number of macro cell network devicesconnected to the network device.
 8. A system, comprising: a processor;and a memory that stores executable instructions that, when executed bythe processor, facilitate performance of operations, comprising:generating network neighbor device data of a set of macro networkdevices comprising macro coverage zones and a set of micro networkdevices comprising micro coverage zones that overlap with the macrocoverage zones, wherein the set of micro network devices and the set ofmacro network devices are communicatively coupled to a macro networkdevice of a heterogeneous network; and in response to detecting atrigger event indicating a failure of the macro network device toestablish a network connection with a network device, the operationscomprising: determining a capacity number of network connections withthe macro network device based on the network neighbor device data;determining a threshold number, from the network neighbor device data,representing the set of micro network devices with which the macronetwork device is operable to establish the network connection based onthe capacity number of network connections and a number of macro networkdevices of the set of macro network devices; and maintaining a definednumber of micro network devices that is less than the threshold numberof the network neighbor device data.
 9. The system of claim 8, whereinthe maintaining the defined number of micro network devices that is lessthan the threshold number of the network device data comprisesfacilitating the network connection with an additional micro networkdevice, and wherein a number of the set of micro network devices inconnection with the macro network device is greater than the definednumber of micro network devices.
 10. The system of claim 9, wherein themaintaining the defined number of micro network devices that is lessthan the threshold number of the network device data comprises:generating a rank of the set of micro network devices based on an attachattempt rate; and removing the network connection of at least one micronetwork device to the macro network device based on the rank.
 11. Thesystem of claim 8, wherein the operations further comprise modifying thethreshold number in response to an additional macro network device ofthe set of macro network devices being determined to have establishedthe network connection with the macro network device, and wherein thedefined number of micro network devices is at least two less than thethreshold number determined from the network neighbor device data. 12.The system of claim 9, wherein the operations further comprise modifyingthe threshold number in response to at least one macro network device ofthe set of macro network devices being determined to have been removedfrom the network connection with the macro network device, and whereinthe defined number of micro network devices is at least two less thanthe threshold number of the network neighbor device data.
 13. The systemof claim 9, wherein the set of macro network devices and the set ofmicro network devices are communicatively coupled to the macro networkdevice by an X2 interface connection.
 14. A machine-readable storagemedium comprising executable instructions that, when executed by aprocessor, facilitate performance of operations, comprising: generatingnetwork neighbor device data representing micro network devicecandidates that neighbor a macro network device in a heterogeneousnetwork comprising micro network devices and macro network devices for apotential transfer from the macro network device; in response to atrigger event that indicates a failure to establish a neighbor relationwith the macro network device, determining a threshold number of micronetwork devices with which the macro network device is operable toestablish the neighbor relation, and maintaining a defined size of thenetwork neighbor device data representing the micro network devicecandidates that is less than the threshold number of micro networkdevices with which the macro network device is operable to establish theneighbor relation; and facilitating an additional neighbor relation withan additional micro network device, not included in the threshold numberof micro network devices, that is detected within the heterogeneousnetwork.
 15. The machine-readable storage medium of claim 14, whereinthe facilitating the additional neighbor relation with the additionalmicro network device is further initiated in response to the triggerevent that indicates the failure to establish the neighbor relation withthe macro network device.
 16. The machine-readable storage medium ofclaim 14, wherein the maintaining the defined size of the networkneighbor device data comprises: in response to the facilitating theadditional neighbor relation with the additional micro network device,generating a priority of the micro network device candidates of thenetwork neighbor device data, and removing at least one micro networkdevice candidate from the network neighbor device data based on thepriority.
 17. The machine-readable storage medium of claim 16, whereinthe generating the priority comprises determining corresponding attachattempts to the micro network device candidates.
 18. Themachine-readable storage medium of claim 17, wherein the removing of theat least one micro network device candidate is based on a rank of themicro network device candidates according to the corresponding attachattempts.
 19. The machine-readable storage medium of claim 16, whereinthe removing of the at least one micro network device candidate is basedon a rank of the micro network device candidates according to a rate ofcorresponding attach attempts to the micro network device candidates.20. The machine-readable storage medium of claim 14, wherein thedetermining the defined size of the network neighbor device datarepresenting the micro network device candidates is based on a number ofmicro cell network device candidates corresponding to the macro networkdevices.